Introduce namespace restriction on pod alerts#160
Merged
t-margheim merged 1 commit intomainfrom Mar 3, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a namespace restriction to pod-based alerts in Grafana. Specifically, our default alerts will monitor only Posit Team specific namespaces and monitoring related namespaces. Other namespaces were excluded since pod failures in those namespaces will trigger downstream alerts (if Calico networking fails, the healthcheck alerts will fire). This also means that custom, unrelated pods running in the same workload cluster as a managed PTD deployment will not trigger PTD alerts.
Category of change